Integration of triple tags into a tagging tool and text browsing

ABSTRACT

Techniques for integrating triple tags into a tagging tool are described herein. According to one embodiment, tags used to tag document pages and associated with one or more communities are stored in a storage as a triple store, where each tag is stored in a format having a subject, a predicate, and an object fields representing a relationship among each tag, an associated document page, and associated communities. A tag input field is displayed in a sidebar window communicatively coupled to a main window of a browser to allow a user to enter a type of tag and an identifier of the tag in the tag search field, such that the entered tag can be stored within the triple store in view of the tag type and tag identifier. Other methods and apparatuses are also described.

COPYRIGHT NOTICES

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

The present invention relates generally to managing tagged documentpages. More particularly, this invention relates to integrating tripletags into tagging tool and text browsing.

BACKGROUND

Web browsers are programs that serve as a front end to the World WideWeb on the Internet. In order to view a Web site, its address, i.e.Uniform Resource Locator (URL), is typed into the Web browser's locationfield and the home page of that Web site is downloaded to the Webbrowser. The home page is an index to other Web pages on that site thatcan be accessed by clicking a message or an icon on the home page. Thehome page is either received in a Hypertext Markup Language (HTML)format or is converted to an HTML format by the Web browser fordisplaying to the user.

Using a browser, a user may visit a large number of web sites in variousbrowser sessions. At each web site, a user may also visit multiple webpages during an individual browser session. In some cases, a descriptionand an address (e.g., the Uniform Resource Locator or URL) for a webpage visited during a browser session may be saved in a sequential,stack-based “history” list, possibly allowing a user to return to apreviously visited web page by selecting its description from thehistory list. A user can open the history list to select previouslyviewed resources, which are usually identified by the title or addressof the web page. A user can also “bookmark” a currently viewed web pagein a favorites list to facilitate selection of the bookmarked resourcefrom the Favorites list for a later visit.

Certain resources may be tagged or managed based on certain criteria.However, there has been lack of user friendly environment to managecertain resources such as bookmarked Web pages or resources.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings in which likereferences indicate similar elements.

FIG. 1 is a block diagram illustrating an example of a network systemaccording to one embodiment of the invention.

FIGS. 2A-2K are screenshots illustrating examples of graphical userinterfaces (GUIs) of a tag browsing framework according to certainembodiments of the invention.

FIG. 3 is a flow diagram illustrating a process for managing taggeditems according to one embodiment of the invention.

FIGS. 4A-4C are screenshots illustrating an example of GUI of a sidebarapplication according to one embodiment of the invention.

FIG. 5 is a flow diagram illustrating a process performed via a sidebarapplication according to one embodiment.

FIGS. 6A-6C are screenshots illustrating an example of GUIs ofconfiguring a sidebar framework according to one embodiment of theinvention.

FIG. 7 is a block diagram illustrating a data processing system whichmay be used with an embodiment of the invention.

DETAILED DESCRIPTION

In the following description, numerous details are set forth to providea more thorough explanation of the embodiments of the present invention.It will be apparent, however, to one skilled in the art, thatembodiments of the present invention may be practiced without thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form, rather than in detail, in order toavoid obscuring embodiments of the present invention.

Reference in the specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the invention. The appearances of the phrase “in one embodiment” invarious places in the specification do not necessarily all refer to thesame embodiment.

FIG. 1 is a block diagram illustrating an example of a network systemaccording to one embodiment of the invention. Referring to FIG. 1,system 100 includes a computer system 102 communicatively coupled toremote systems 104-106 over a network 108. System 102 may be a client ora server system and systems 104-106 may be server systems such as a Webserver or a network-based data storage system. Network 108 may be a widearea network (WAN) such as Internet, a local area network, or acombination of both. For purposes of illustration, throughout thisapplication, systems 104-106 are described as Web servers and system 102is described as a client system. Similarly, network 108 is described asthe Internet. However, it will be appreciated that other configurationsmay exist.

Referring back to FIG. 1, system 102 includes a browser application 110(e.g., Web browser) such as Internet Explorer™ available from MicrosoftCorporation of Redmond, Wash. or Firefox™ available from Mozilla ofMountain View, Calif. System 102 further includes a browser plug-inapplication 112 (also referred to as a browser companion framework)communicatively coupled to the browser application 110. In oneembodiment, browser plug-in application 112 is able to access contentdisplayed in a main window 118 of browser 110 in which a tag browsingapplication 116 may display certain tagged items or resources in themain window 118. For example, the plug-in application 112 may display orpop up a tag sidebar communicatively coupled to the main window 118.Within the tag sidebar, one or more portlets (e.g., portal pages) may bedisplayed for a variety of purposes, such as, for example, tagging,search request, and/or case management purposes.

In one embodiment, an extension associated with browser application 110sets up the necessary security settings such that a web application(e.g., a plug-in application such as browser plug-in application 112)calling in the browser sidebar can access information from the mainwindow 110, such as, for example, a URL or universal resource locator.For example, the plug-in application 112 may install a button or controlthat calls a portal page (e.g., portlets 114) to be loaded in thebrowser sidebar (not shown). The portal can serve any kind of portletsthat acts as “browsing companions”, such as, for example, a searchrequest portlet and a case management portlet which profit from beingavailable at the same time as a user works on several other tabs in themain window 118.

In one embodiment, the framework 112 may further include a “watchdog”(not shown) that watches the URL of the main page in an optimized way.For example, the watchdog is aware of a currently active tab, it isalmost in real time without firing too much (e.g. when a user scrollsthrough his/her tabs) requests or calls. That is useful because thesidebar might fire a new request for the sidebar page on every change ofthe main window URL. Generally, the sidebar does not do a full pagerefresh on a change to the main window URL, rather the contained Javascript objects get informed, and the Java script objects fire small AJAX(Asynchronous Java Script and XML) requests to update their content.

AJAX applications are mainly executed on the user's machine, bymanipulating the current Web page within their browser using documentobject model (DOM) methods. AJAX can be used for a multitude of taskssuch as updating or deleting records; expanding Web forms; returningsimple search queries; or editing category trees—all without therequirement to fetch a full page of HTML each time a change is made.Generally, only small requests need to be sent to the server, andrelatively short responses are sent back. This permits the developmentof more interactive applications featuring more responsive userinterfaces due to the user of DHTML (Dynamic HTML) techniques.

The scripting application or applications running at the server may bedeveloped using frameworks and technologies based on several popularplatforms, including Macromedia Flash, Sun Java, Microsoft ASP. NET,DHTML (Dynamic HTML), JavaScript, HTML, Extensible Markup Language(XML), cascading style sheets (CSS), the Document Object Model (DOM),and the Microsoft XMLHTTPRequest object, etc.

Referring back to FIG. 1, a tagging sidebar portlet is a portal pagesitting in the browser sidebar and showing all tags that are given tothe page viewed in the main browser window 118. In one embodiment, thereis an input field for new tags, and a checklist of communities, to whicha user may want to assign newly given tags. Checking a checkbox such as“show tag details” may reveal date, author and communities of giventags. Details can be edited (e.g. tags can be removed from certaincommunities). An AJAX mechanism may be used to suggest existing tagswhen entering a tag, ordering the suggestion by popularity, thuscontributing to a consolidated tag base.

In one embodiment, a tag browsing application 116 (e.g., a knowledgebrowser) includes three main areas: a resource list, a communities box,and a tag box on startup, where the resource list shows all taggedresources in any community. A tag box shows a list of all available tagsin a particular community or communities. The communities box shows oneor more checkboxes for the available communities (all checked bydefault), and a special “only my tags” checkbox (by default unchecked).If a user unselects some of the communities, the list of resourceschanges to show only the tags associated with the checked communities.If the user checks the “only my tags” checkbox, only the tags associatedwith the user are shown.

In one embodiment, the tag box shows a list of all available tags (inthe checked communities). If a user selects a tag, the list of resourcesis updated in real time to show only the resources that are tagged withthis tag in the checked community. In addition, according to oneembodiment, there is another section such as “related” tags in the tagbox, which shows any other tags that are available on any resourcealready filtered by the first tag (in the checked communities). If auser clicks on one of the related tags, the resource list only showsresources that have both of the tags, and the list of related tags isupdated correspondingly. This allows for a fast drill down on theexisting tagged resources by their aspects.

Referring back to FIG. 1, tag stores 106 may be implemented as a serveror a data storage system to store the resources such as URLs of certainWeb pages or documents tagged by one or more users of one or morecommunities, when those users browse or access certain Web sites such asWeb servers 104 over the Internet 108. In one embodiment, the tag storebackend 108 is implemented as a triple store, so every tag can have atag type. This makes it easy to export the tag space into a RDF(resource description framework) format for further processing, datamining, or extension of functionality. Power users can enter tags in theform Tagtype:tag (e.g. Format:Tutorial).

Note that each tagged document or Web page may be stored in tag store106 and associated with a URL, such that a tagged page or document maybe accessed via the URL by any user that browses using the framework.For example, a first user may browse and find a particular tagged pageand email the associated URL to a second user. The second user may then“pick up” the URL to access the tagged page. Thus, each tagged pageseems to be stored in a persistent storage and identified by acorresponding URL. Such a tagged page can accessed via the associatedURL at any time by any user.

To not confuse standard users, by default tags are interpreted as beingof type “keyword”, and the tag type is not shown. If a tag with adifferent type is chosen from autosuggest, the newly given tag will usethe chosen tags type. Even though much of the tag type functionality ishidden from the user, it also allows for neat tricks like entering“Format:” into the tagging sidebar input field, and autosuggest willcome up with the available tags of this type: Reference, Tutorial,Article, etc. The same works for “Product:” and “Publishlevel:” and anyother tag type that the user chooses to create. Note that some or all ofthe components as shown in FIG. 1 may be implemented in software,hardware, or a combination of both. Other configurations may also exist.

FIGS. 2A-2K are screenshots illustrating examples of graphical userinterfaces (GUIs) of a tag browsing framework according to certainembodiments of the invention. For example, GUIs as shown in FIGS. 2A-2Mmay be implemented as part of a browser companion frameworkcommunicating with a Web browser as described above with respect to FIG.1.

Referring to FIG. 2A, according to one embodiment, GUI 200 includes amain browsing window 202 and a sidebar window 204, which may be aplug-in application to the browser 200. In one embodiment, browser 200may include a specific plug-in interface having certain security measureto allow sidebar 204 to access the content displayed in the main window202. In addition, sidebar 204 includes one or more buttons or links 206,which when activated, additional information such as windows or pagesmay be displayed. According to one embodiment, sidebar 204 furtherincludes a tag area 208 having a variety of fields such as search andinput fields to allow a user to search certain tags or enter a new tag,which will be described in details further below.

According to another embodiment, sidebar 204 further includes a feedarea 210 to allow a user to subscribe information feed with respect toupdates or changes associated with a particular tag, where theinformation is actively fed, for example, via an RSS (sometimes alsoreferred to as really simple syndication, RDF site summary, or rich sitesummary) feed mechanism, to the user.

RSS is a family of Web feed formats used to publish frequently updatedcontent such as blog entries, news headlines or podcasts. An RSSdocument, which called a “feed,” “Web feed,” or “channel,” containseither a summary of content from an associated Web site or the fulltext. RSS makes it possible for people to keep up with their favoriteWeb sites in an automated manner that is easier than checking themmanually. RSS content can be read using software called an “RSS reader,”“feed reader” or an “aggregator.” The user subscribes to a feed byentering the feed's link into the reader or by clicking an RSS icon in abrowser that initiates the subscription process. The reader checks theuser's subscribed feeds regularly for new content, downloading anyupdates that it finds.

Referring back to FIG. 2A, from sidebar 204, a tag browser page may beactivated via a corresponding link (e.g., “Knowledge Browser”) from menubar 206, as shown in FIG. 2B. Referring to FIG. 2B, the tag browser pageincludes, but not limited to, a resource display area 212, a tag displayarea 214, and a community display area 216. Resource display area 212 isused to display a list of resources, such as links having correspondingURLs, which include one or more tags displayed in tag display area 214,which may be implemented as a portlet and associated with one or morecommunities selected in the community display area 216, which may alsobe implemented as a portlet.

In one embodiment, tag display area 214 includes a tag area 218 havingall tags in which at least one of them is associated with at least oneresource displayed in resource display area 212. The tag display area214 further includes a related tag area 220 having one or more tags thatmay be related to one or more tags displayed in tag area 218. Any of thetags displayed in area 214 may be selected or unselected by a user whichin turn causes certain resources displayed or removed from resourcedisplay area 212. Similarly, any of the communities displayed incommunity area 216 may also be selected and unselected which also inturn causes certain resources to be displayed or removed from displayarea 212. Note that the resources displayed in resource area 212 onlyinclude those having one or more tags displayed in area 214 andassociated with one or more selected communities displayed in area 216.Thus, by changing the selections in areas 214 and 216, correspondingresources displayed in area 212 will be displayed and changeddynamically.

For example, as shown in FIG. 2C, when a user selects one or more tagsfrom tag display area 214, resources (e.g., tagged pages) displayed inresource display area 212 will change. In this example, the user selectstag “application_development,” which is shown in display area 222indicated what tags have been selected. As a result, the resourcedisplay area 212 will dynamically display only the resources containingor associated with the selected tag of “application_development.”Without selecting tag of “application_development,” the resource displayarea 212 displays all resources that contain or are associated with oneor more tags display in tag area 218. By selecting a tag, the resourcesdisplayed in area 212 will be filtered based on the selected tag.

In addition, one or more related tags may be displayed in the relatedtag area 220. In this example, the related tags include a related tag“reference”, which will further filter the resources displayed inresource display area 212. Now, by selecting tags“application_development” and “reference”, which are shown in displayarea 224, the tagged resources are further filtered down and displayedin resource display area 212, as shown in FIG. 2D. Similarly, as shownin FIG. 2D, any of the selected tags displayed in area 222 may beremoved or unselected, for example, by clicking button or control“remove” and the corresponding resource list displayed in resourcedisplay area 212 will be updated accordingly.

Furthermore, according to one embodiment, resources displayed inresource display area 212 may be further filtered by selecting and/orunselected one or more communities displayed in community area 216. Forexample, any of the communities 226 displayed in area 216 may beselected or unselected. Any selection or unselection of any communitymay causes the resources displayed in resource display area 212 tochange. In addition, according to one embodiment, a user may select “mybookmarks only” 228 to shown those resources that are tagged orassociated with the user itself, for example, as shown in FIG. 2K.

According to a further embodiment, referring to FIG. 2D, a user maysubscribe any update from any of the resources listed in resourcedisplay area 212 by clicking, activating, or associating RSS feed 230with any of the resources. Similarly, a user may also subscribe anyupdate from any of the communities displayed in community area 216 byclicking, activating, or associating RSS feed 232 with any of thecommunities, selected or unselected, displayed in area 216.

According to yet another embodiment, the list of resources may befiltered based on users or authors associated with the resources.Referring to FIG. 2E, each tagged page or resource displayed in resourcedisplay area 212 has been tagged or saved by a particular user orauthor. For example, resource 233 listed in resource display area 212was saved or tagged by user or author 234. User 234 may be displayed asa link or control, which when activated or selected, causes allresources tagged by or associated with the selected user as shown inFIG. 2F. In addition, those resources displayed in resource display area212 include one or more tags displayed in tag display area 214 and areassociated with one or more selected communities displayed in communityarea 216. Accordingly, display area 224 also updates that the currentlylisted resources are tagged by the selected user.

As described above, a user can subscribe an RSS feed for any of thetagged items to receive updates associated with the selected taggeditems. Referring now to FIG. 2G, in this example, items displayed inresource display area 212 have been tagged with keywords listed indisplay area 224. When a user wishes to subscribe an RSS feed on any ofthe tagged items, the user may click or activate RSS feed control orlink 230, which causes a menu 236 of actions to be displayed as shown inFIG. 2H. The user then may select any of the actions which may cause anRSS subscription page to be displayed as shown in FIG. 2I.

Note that, for the purposes of illustration, throughout thisapplication, each of the above GUI pages may also be referred to as a“view.” A “view” of the knowledge browser represents any or a particularstate of the knowledge browser being associated with a set of selectedcommunities, a selected tags, optionally a selected user or users (e.g.,might be the current user). Each such a “view” can be associated with aURL that will recreate that view at any time (e.g., subsequently),although dynamically displaying the resources that fit that view in theunderlying tag store at the time that the URL is called. The GUI asshown in FIG. 2I includes a subscription button which when activated,causes RSS feed reader (or a representation of it) to be built. In oneembodiment, what is actually built is the Javascript code that generatesa feed reader application into any Web page where the code is pasted.Referring now to FIG. 2J, when a user decides to subscribe an RSS feedon any of the views, an RSS feed reader is built and displayed in window238, including the code (e.g., Java script) that implements the feedreader in window 240. The code can then be generated from each of theviews that the user wishes to subscribe. Note that GUIs as shown inFIGS. 2A-2K are described for the purposes of illustration only; otherconfigurations may exist.

FIG. 3 is a flow diagram illustrating a process for managing taggeditems according to one embodiment of the invention. Note that process300 may be performed by processing logic which may include software,hardware, or a combination of both. For example, process 300 may beperformed by systems as shown in FIGS. 1 and 2A-2K. Referring to FIG. 3,at block 302, a community area having one or more selectable communitiesis displayed within a Web browser. At block 304, a tag display areahaving one or more tag keywords is displayed within the Web browser,where the tag keywords are selectable and capable of being tagged in adocument page (e.g., Web page). At block 306, processing logic displayswithin the Web browser a main display area having a list of one or moreresources or tagged items (e.g., represented via URLs) that have beentagged by at least one of the keywords displayed in the tag display areaand associated with at least one of the communities displayed in thecommunity area. At block 308, in response to a selection of at least oneof the tags displayed in the tag display area, a related tag displayarea is displayed having one or more tags that are related to theselected tags.

At block 310, in response to a selection of a community in the communitydisplay area, processing logic dynamically updates content displayed inthe main display area, the tag display area, and/or the related tagdisplay area. Only the content is associated with the selected one ormore communities will be displayed in these areas. At block 312, inresponse to a selection of a tag keyword in the tag display area,processing logic dynamically updates content displayed in the maindisplay area and the related tag display area. Only the content havingat least one selected tag is displayed in the main display area and onlythe content related to the at least one selected tag will be displayedin the related tag area. In one embodiment, when no tags are selected,the resource list shows just all pages that are tagged “as anything” inthe selected communities and/or by the selected user. This is useful,especially together with the secondary features of the knowledgebrowser: E.g., a user can subscribe to that “any tag” view in a feedreader, alerting the user whenever a tag arrives in user's community, orthe user can subscribe to any tag by a certain user, making it easy tofollow the flow of that user. Or a community website could include alist of resources recently tagged for that community. At block 314, inresponse to a selection of a tag in the related tag area, processinglogic dynamically updates the content displayed in the main display areasuch that only the content tagged by the selected keywords in theregular tag area and the related tag area will be displayed. Otheroperations may also be performed.

FIGS. 4A-4C are screenshots illustrating an example of GUI of a sidebarapplication according to one embodiment of the invention. Note that GUIsas shown in FIGS. 4A-4C may be performed by the system as shown in FIG.1 and may be implemented in conjunction with GUIs as shown in FIGS.2A-2K. For the purpose of consistency, certain reference numbers aremaintained the same with respect to FIGS. 2A-2K. Referring to FIG. 4A,as described above, a Web browser includes a plug-in application asshown as a sidebar window 204 which is communicatively coupled to themain window of the browser having, for example, resource display area212, tag display area 214, and community display area 216 as describedabove. Sidebar window 204 may be displayed in response to an activationof a button or a selection from a menu. As described above, sidebarwindow 204 includes a shortcut area 206 having one or more shortcut orlinks which when activated may display a further page such as tagbrowser pages as shown in FIGS. 2A-2K. In addition, sidebar window 204includes a tag portlet 208 and a feed portlet 210.

According to one embodiment, tag portlet 208 is configured to allow auser to add and maintain metadata on Web pages or other document pages.Tagging means assigning tags (e.g., keywords or terms) to some pieces ofinformation. Tagging Web pages can be compared to using bookmarks in abrowser. The difference is tags having no tree structure and thus, auser never wonder how to organize them. Making tags public allows otherusers to search them. Community tagging means sharing tags among aspecific group of users.

Referring back to FIG. 4A, tags can be searched via a search field 402.When a user enters a keyword for searching in the search field 402, anauto-completion feature may be used to provide suggestions to the userto choose the right or existing tags. The URL of a specific pagecurrently displayed in the main window is shown in URL area 404 ofsidebar window 204. This is useful because the Web page having a URL isstored persistently in a tag store to allow other users to subsequentlysearch and retrieve from the tag store. Further, a user can tag aspecific page to a specific community via interface 406. This wouldpublish the tagged item or page among members of one or more communitiesassigned.

According to one embodiment, a user can also add a new tag via tag inputfield 408. Typically, a user may open the sidebar 204 and browse to apage that the user would like to tag. The user must always tag in atleast one community by checking at least one community and enter the tagor tags in the tag input field 408. The user may also enter certainnotes associated with the new tag via an add note interface 412. Thedetail of the newly entered tags may be shown via link 410, includingdate, authors, and communities of given tags assigned to the page shownin the main window. The details can also be edited (e.g., removed fromcertain communities). Each of the new tags may be removed or deleted,for example, by clicking a delete or remove button associated with thetag. Similarly, a selected community may also be removed or unselectedin a similar way; however, a tag must be associated with at least onecommunity. A list of communities associated with a user may beconfigured via a configuration page of the sidebar 204, such as, forexample, via a “config” shortcut in the shortcut area 206, which will bedescribed in details further below.

According to one embodiment, by tagging RSS feeds with sidebar news tag,a user makes them appear in the feed portlet 210, visible for every userwho has registered in the associated community sidebar news tag.According to another embodiment, sidebar 204 further provides full-textsearch features in a full-text search portlet 414. A user can define asearching scope by checking the collections and the choice depends onthe communities the user registered in.

In one embodiment, when a user enters a keyword or new tag in the taginput field 408, a list of suggested similar keywords or terms, and/orexisting tags may be displayed as shown in FIG. 4B. Referring to FIG.4B, when the user enters the first one or more characters in the taginput filed 408, a list of suggested similar keywords or terms, and/orexisting tags is displayed in a pull-down menu or window 416 from whichthe user can select one of terms from the menu 416 as part ofauto-completion. In one embodiment, a number of pages that have beentagged with each suggested tag or term may also be displayed.

Alternatively, as shown in FIG. 4C, the user may enter a keyword with a“type:tag” format. As a result, the auto-completion feature may onlydisplay the terms or tags associated with the specified type. In oneembodiment, a number of pages that have been tagged with each suggestedtag or term may also be displayed. Note that the tag store (e.g., tagstore 106 of FIG. 1) may be implemented as a triple store. Thus, everytag can have a tag type. An advanced user can enter tags in the form of“tagtype:tag” such as “format:tutorial”, This makes it easy to exportthe tag space into RDF formats for further processing, data mining, orextension of functionality.

RDF (resource description framework) is a family of Word Wide WebConsortium (W3C) specifications originally designed as a metadata modelbut which has come to used as a general method of modeling informationthrough a variety of syntax formats. The RDF metadata model is based onthe idea of making statements about resources in the form ofsubject-predicate-object expressions, called “triples” in RDFterminology. The subject denotes the resource, and the predicate denotestrials or aspects of the resource and expresses a relationship betweenthe subject and the object. For example, one way to represent the notion“The sky has the color blue” in RDF is as a triple of speciallyformatted strings: a subject denoting “the sky,” a predicate denoting“has the color,” and an object denoting “blue.” This mechanism fordescribing resources is a major component in what is proposed by theW3C's Semantic Web activity: an evolutionary stage of the World Wide Webin which automated software can store, exchange, and usemachine-readable information distributed throughout the Web, in turnenabling users to deal with the information with greater efficiency andcertainty. RDF's simple data model and ability to model disparate,abstract concepts has also led to its increasing use in knowledgemanagement applications unrelated to Semantic Web activity.

A collection of RDF statements intrinsically represents a labeled,directed pseudo-graph. As such, an RDF-based data model is morenaturally suited to certain kinds of knowledge representation than therelational model and other ontological models traditionally used incomputing. However, in practice, RDF data is often stored in relationaldatabase representations, also referred to as “triple stores.” Thesubject of an RDF statement is a resource, which may be as named by aURI (uniform resource identifier). Some resources are unnamed and arecalled blank nodes or anonymous resources. They are not directlyidentifiable. The predicate is a resource as well, representing arelationship. The object is a resource or a Unicode string literal.

In semantic Web applications and in relatively popular applications ofRDF such as RSS and FOAF (friend of a friend), resources tend to berepresented by URIs that intentionally denote actual, accessible data onthe World Wide Web. But RDF, in general, is not limited to thedescription of Internet-based resources. In fact, the URI that names aresource does not have to be referenceable at all. For example, a URIthat begins with “http:” and is used as a subject of an RDF statementdoes not necessarily have to represent a resource that is accessible viaHTTP, nor does it need to represent a tangible, network-accessibleresource.

FIG. 5 is a flow diagram illustrating a process performed via a sidebarapplication according to one embodiment. Note that process 500 may beperformed by processing logic which may include software, hardware, or acombination of both. For example, process 500 may be performed by thesystem as shown in FIGS. 1 and 4A-4C. Referring to FIG. 5, at block 502,processing logic displays a sidebar window within a browser, where thesidebar window is communicatively coupled to a main window of thebrowser via a plug-in interface. At block 504, in response to an inputentered in a tag search field, processing logic displays a Web page inthe main window having a list of resources that have been tagged withthe input. At block 506, in response to an input entered in a tag inputfield of the sidebar window, the page displayed in the main window istagged with the input of the tag input field as a new tag. At block 508,processing logic displays a list of suggested words while the input isbeing entered in the tag input field to allow a user to select one ofthe suggested terms or tags as part of auto-completion. At block 510,processing logic displays a number of items that have been tagged foreach of the suggested terms suggested for the input being entered in thetag input field. At block 512, processing logic displays within thesidebar window a feed subscription field to allow a user to subscribeinformation fed from one or more selected resources displayed in themain window. At block 514, the processing logic displays a full-textsearch field within the sidebar window to allow a user to perform afull-text search within certain categories or communities which can beselected within the sidebar window. Other operations may also beperformed.

FIGS. 6A-6C are screenshots illustrating an example of GUIs ofconfiguring a sidebar framework according to one embodiment of theinvention. Referring to FIG. 6A, when a user clicks a shortcut “config”of shortcut menu 206, a configuration page is displayed in the mainwindow 202. The configuration page includes certain areas or fields toallow the user to configure how the sidebar framework operates. Forexample, a user can select or unselect any of the communities displayedin area 602. When the user clicks the submit button the selectedcommunities may show up in the sidebar window 204.

In addition, the user can import certain tags from an externalenvironment or framework. For example, a user can activate a link 604which may prompt the user, via the dialog box 606, to login in theenvironment from which the tags to be imported from, as shown in FIG.6B. Once the user logs in, as shown in FIG. 6C, an import page isdisplayed in the main window. Referring to FIG. 6C, the import pageincludes list of resources or posts displayed in area 608. Each of theposts displayed can be select or unselected by clicking thecorresponding checkbox. Similar to the tag browser application, each ofthe posts is displayed dependent upon the selection in the community box610 the tag selection in the tag box 612.

For example, each of the tags displayed in area 612 can be selected orunselected by clicking the corresponding check sign 618. Similar to thetag browser application described above, the posts 608 change as theuser clicks. In addition, color in conjunction with the sign can be usedto indicate the specific status of the tag. For example, a red crossmeans no posts with this tag are selected; pale green means some of thebookmarks are selected; and green check means all of them are selected.If a user specifically wants to exclude or include certain tags, theuser can lock the selection or unselection of a tag by clicking thecorresponding lock icon 620.

Further, one or more filters may be specified in a filter field 614 andicons 614 may be used to add or remove a filter. A user can enter in anystring and all bookmarks with addresses matching it will be selected orunselected. Later on the user can delete a filter by clicking a binicon, or toggle its selection state. A user can have any number offilters active. The user can also select certain communities the postsshould be saved to. Finally, the user can share the selected bookmarkswith others in the selected communities by clicking button 622. Otherconfigurations may exist.

FIG. 7 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed. In alternative embodiments, themachine may be connected (e.g., networked) to other machines in a LocalArea Network (LAN), an intranet, an extranet, or the Internet. Themachine may operate in the capacity of a server or a client machine in aclient-server network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine may be apersonal computer (PC), a tablet PC, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, aserver, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines (e.g., computers) that individuallyor jointly execute a set (or multiple sets) of instructions to performany one or more of the methodologies discussed herein. For example, thesystem 700 may be used as part of system, either a client or a server,as shown in FIG. 1.

As shown in FIG. 7, the system 700, which is a form of a data processingsystem, includes a bus or interconnect 702 which is coupled to one ormore microprocessors 703 and a ROM 707, a volatile RAM 705, and anon-volatile memory 706. The microprocessor 703 is coupled to cachememory 704 as shown in the example of FIG. 7. Processor 703 may be, forexample, a PowerPC microprocessor or an Intel compatible processor.Alternatively, processor 703 may be a digital signal processor orprocessing unit of any type of architecture, such as an ASIC(Application-Specific Integrated Circuit), a CISC (Complex InstructionSet Computing), RISC (Reduced Instruction Set Computing), VLIW (VeryLong Instruction Word), or hybrid architecture, although any appropriateprocessor may be used.

The bus 702 interconnects these various components together and alsointerconnects these components 703, 707, 705, and 706 to a displaycontroller and display device 708, as well as to input/output (I/O)devices 710, which may be mice, keyboards, modems, network interfaces,printers, and other devices which are well-known in the art.

Typically, the input/output devices 710 are coupled to the systemthrough input/output controllers 709. The volatile RAM 705 is typicallyimplemented as dynamic RAM (DRAM) which requires power continuously inorder to refresh or maintain the data in the memory. The non-volatilememory 706 is typically a magnetic hard drive, a magnetic optical drive,an optical drive, or a DVD RAM or other type of memory system whichmaintains data even after power is removed from the system. Typically,the non-volatile memory will also be a random access memory, althoughthis is not required.

While FIG. 7 shows that the non-volatile memory is a local devicecoupled directly to the rest of the components in the data processingsystem, embodiments of the present invention may utilize a non-volatilememory which is remote from the system; such as, a network storagedevice which is coupled to the data processing system through a networkinterface such as a modem or Ethernet interface. The bus 702 may includeone or more buses connected to each other through various bridges,controllers, and/or adapters, as is well-known in the art. In oneembodiment, the I/O controller 709 includes a USB (Universal Serial Bus)adapter for controlling USB peripherals. Alternatively, I/O controller709 may include an IEEE-1394 adapter, also known as FireWire adapter,for controlling FireWire devices.

Some portions of the preceding detailed descriptions have been presentedin terms of algorithms and symbolic representations of operations ondata bits within a computer memory. These algorithmic descriptions andrepresentations are the ways used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the above discussion, itis appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

Embodiments of the present invention also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, or it may comprise ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program may bestored in a computer readable medium. A machine-readable medium includesany mechanism for storing or transmitting information in a form readableby a machine (e.g., a computer). For example, a machine-readable (e.g.,computer-readable) medium includes a machine (e.g., a computer) readablestorage medium (e.g., read only memory (“ROM”), random access memory(“RAM”), magnetic disk storage media, optical storage media, flashmemory devices, etc.), a machine (e.g., computer) readable transmissionmedium (electrical, optical, acoustical or other form of propagatedsignals (e.g., carrier waves, infrared signals, digital signals, etc.)),etc.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general-purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method operations. The requiredstructure for a variety of these systems will appear from thedescription below. In addition, embodiments of the present invention arenot described with reference to any particular programming language. Itwill be appreciated that a variety of programming languages may be usedto implement the teachings of embodiments of the invention as describedherein.

In the foregoing specification, embodiments of the invention have beendescribed with reference to specific exemplary embodiments thereof. Itwill be evident that various modifications may be made thereto withoutdeparting from the broader spirit and scope of embodiments of theinvention as set forth in the following claims. The specification anddrawings are, accordingly, to be regarded in an illustrative senserather than a restrictive sense.

What is claimed is:
 1. A method, comprising: displaying a tag inputfield in a sidebar window communicatively coupled to a main window of abrowser to allow a user to enter a type of tag and an identifier of thetag in the tag input field; in response to content entered from the userin the tag input field, detecting whether the entered content specifiesa tag type according to a format, the format comprising a triple fieldformat; displaying within the sidebar window a list of existing tags asa suggestion of tags that are associated with the tag type entered inthe tag input field, if it is determined that the entered contentspecifies a tag type, to allow the user to select from the list ofexisting tags as part of auto-completion of a tag identifier withouthaving the user enter the tag identifier in the tag input field, whereinthe existing tags are stored in a format having a subject field, apredicate field, and an object field that are used to represent arelationship between the existing tags, an associated document page andan associated community; and associating, by a processing device, anaddress of a document page currently displayed in the main window withthe selected tag, the selected tag representing a keyword to label theassociated document page, such that the document page is subsequentlyretrievable via the address based on searching of the associated tag,without having to search based on content of the associated documentpage, wherein the selected tag is also associated with other relateddocument pages in addition to the document page currently displayed inthe main window.
 2. The method of claim 1, wherein the a triple fieldformat according to a resource description framework (RDF)specification.
 3. The method of claim 2, further comprising, for each ofthe existing tags associated with the tag type, displaying within afirst display area of the main window resources representing a number ofdocument pages that have been tagged by each existing tag.
 4. The methodof claim 3, further comprising: displaying in a second display area ofthe main window a list of one or more communities in which the selectedtag has been published, wherein each of the one or more communities canbe selectable or unselectable.
 5. The method of claim 4, furthercomprising, in response to selecting or unselecting a community from thesecond display area, dynamically updating resources displayed in thefirst display area, such that only resources associated with remainingselected communities are displayed in the first display area.
 6. Themethod of claim 4, further comprising displaying in a third display areaof the main window a list of tags that are associated with at least onecommunity displayed in the second display area.
 7. The method of claim6, further comprising, in response to selecting or unselecting a tagdisplayed in the third display area, dynamically updating resourcesdisplayed in the first display area, such that only resources tagged bythe tag selected from the third display area are displayed in the firstdisplay area.
 8. The method of claim 6, further comprising displaying ina fourth display area of the main window one or more related tags thatare related to at least one tag displayed in the third display area. 9.The method of claim 8, further comprising, in response to selecting orunselecting a related tag displayed in the fourth display area,dynamically updating resources displayed in the first display area, suchthat only resources that are tagged by the selected tags and the relatedtags are displayed in the first display area.
 10. A non-transitorycomputer readable medium including instructions that, when executed by aprocessing device, cause the processing device to perform operationscomprising: displaying a tag input field in a sidebar windowcommunicatively coupled to a main window of a browser to allow a user toenter a type of tag and an identifier of the tag in the tag input field;in response to content entered from the user in the tag input field,detecting whether the entered content specifies a tag type according toa format, the format comprising a triple field format; displaying withinthe sidebar window a list of existing tags as a suggestion of tags thatare associated with the tag type entered in the tag input field, if itis determined that the entered content specifies a tag type, to allowthe user to select from the list of existing tags as part ofauto-completion of a tag identifier without having the user to enter thetag identifier in the tag input field, wherein the existing tags arestored in a format having a subject field, a predicate field, and anobject field that are used to represent a relationship between theexisting tags, an associated document page and an associated community;and associating, by the processing device, an address of a document pagecurrently displayed in the main window with the selected tag, theselected tag representing a keyword to label the associated documentpage, such that the document page is subsequently retrievable via theaddress based on searching of the associated tag, without having tosearch based on content of the associated document page, wherein theselected tag is also associated with other related document pages inaddition to the document page currently displayed in the main window.11. The non-transitory computer readable medium of claim 10, wherein thetriple field format according to resource description framework (RDF)specification.
 12. The non-transitory computer readable medium of claim11, wherein the operations further comprise, for each of the existingtags associated with the tag type, displaying within a first displayarea of the main window resources representing a number of documentpages that have been tagged by each existing tag.
 13. The non-transitorycomputer readable medium of claim 12, wherein the operations furthercomprise: displaying in a second display area of the main window a listof one or more communities in which the selected tag has been published,wherein each of the one or more communities can be selectable orunselectable.
 14. The non-transitory computer readable medium of claim13, wherein the operations further comprise, in response to selecting orunselecting a community from the second display area, dynamicallyupdating resources displayed in the first display area, such that onlyresources associated with remaining selected communities are displayedin the first display area.
 15. The non-transitory computer readablemedium of claim 13, wherein the operations further comprise displayingin a third display area of the main window a list of tags that areassociated with at least one community displayed in the second displayarea.
 16. The non-transitory computer readable medium of claim 15,wherein the operations further comprise, in response to selecting orunselecting a tag displayed in the third display area, dynamicallyupdating resources displayed in the first display area, such that onlyresources tagged by the tag selected from the third display area aredisplayed in the first display area.
 17. The non-transitory computerreadable medium of claim 15, wherein the operations further comprisedisplaying in a fourth display area of the main window one or morerelated tags that are related to at least one tag displayed in the thirddisplay area.
 18. The non-transitory computer readable medium of claim17, wherein the operations further comprise, in response to selecting orunselecting a related tag displayed in the fourth display area,dynamically updating resources displayed in the first display area, suchthat only resources that are tagged by the selected tags and the relatedtags are displayed in the first display area.
 19. A data processingsystem, comprising: a processor; and a memory to store instructions,which are executable by the processor from the memory, to cause theprocessor to: display a tag input field in a sidebar windowcommunicatively coupled to a main window of a browser to allow a user toenter a type of tag and an identifier of the tag in the tag input field,in response to content entered from the user in the tag input field,detect whether the entered content being entered specifies a tag typeaccording to a format, the format comprising a triple field format,display within the sidebar window a list of existing tags as asuggestion of tags that are associated with the tag type entered in thetag input field, if it is determined that the entered content specifiesa tag type, to allow the user to select from the list of existing tagsas part of auto-completion of a tag identifier without having the userto enter the tag identifier in the tag input field, wherein the existingtags are stored in a format having a subject field, a predicate field,and an object field that are used to represent a relationship betweenthe existing tags, an associated document page and an associatedcommunity, and associate an address of a document page currentlydisplayed in the main window with the selected tag, the selected tagrepresenting a keyword to label the associated document page, such thatthe document page is subsequently retrievable via the address based onsearching of the associated tag, without having to search based oncontent of the associated document page, wherein the selected tag isalso associated with other related document pages in addition to thedocument page currently displayed in the main window.
 20. The dataprocessing system of claim 19, the processor further to, for each of theexisting tags associated with the tag type, display within a firstdisplay area of the main window, resources representing a number ofdocument pages that have been tagged by each existing tag.